https://modernanalyst.com RSS feeds for Business Analyst Community & Resources | Modern Analyst 60 https://modernanalyst.com/Resources/Articles/tabid/115/ID/3810/Gherkin-for-Business-Analysts.aspx#Comments 3 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=3810 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3810&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/3810/Gherkin-for-Business-Analysts.aspx Gherkin is a language used to write acceptance tests. BA's use Gherkin to specify how they want the system to behave in certain scenarios...  It’s a simple language. There are 10 key words (e.g. Given, When, Then). Because it’s a simple language, it’s understandable by the business. As well as being understandable by the business, Gherkin can be understood by an automation tool called Cucumber. That means Cucumber can interpret Gherkin and use it to drive automated tests. This links BA requirements to automated tests. Transform VA Mon, 21 Aug 2017 00:08:00 GMT f1397696-738c-4295-afcd-943feb885714:3810 https://modernanalyst.com/Resources/Articles/tabid/115/ID/3491/A-Case-for-Including-Test-Plan-Efforts-in-Qualifying-for-the-IIBA-CBAP-Exam.aspx#Comments 0 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=3491 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3491&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/3491/A-Case-for-Including-Test-Plan-Efforts-in-Qualifying-for-the-IIBA-CBAP-Exam.aspx Essentially, the IIBA® does not view “testing” as being part of the BA role. Obviously I disagree. When it comes to hours associated with test planning/strategies, the IIBA® should accept them as work experience in qualifying to sit for the CBAP® exam. Transform VA Mon, 18 Apr 2016 09:12:00 GMT f1397696-738c-4295-afcd-943feb885714:3491 https://modernanalyst.com/Resources/Articles/tabid/115/ID/3287/How-not-to-get-lost-in-data-jungle.aspx#Comments 0 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=3287 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3287&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/3287/How-not-to-get-lost-in-data-jungle.aspx Data migration is typically the most forgotten or underestimated component of an IT project which is the process of making a copy of data and moving it from one system to another, preferably without disrupting or disabling active business processes. On some occasions, it is not easy to understand that a data migration is needed in the project and most of the times data migration is not seen as an item that its requirements needs to be captured during analysis phase. That’s why migration related problems begin during development or testing phase when data need is identified or when the data from the old system refuses to fit properly into your new user interfaces or business rules despite the transportation of the old data. For a successful project, the need of a data migration and its requirements must to be identified early beginning of analysis phase and further actions should be reflected to project plan accordingly. But how? Data migration strategies are a whole different detailed topic and they will not be mentioned here but capturing the essentials of data nature is a life-saver activity which is the targeted idea of this work. 1. Will you need a data migration? Identify it during elicitation phase if possible. If not, analysis phase is also ok but be careful and just identify the need as earlier as possible. Ask data related simple questions. Do your requirements mention from the systems need to be shut down? If yes, does this system keeps any data? Is your project a replacement project for an old system? If yes, does this system keeps any data? Do your requirements mention from entities that are already used in your company’s systems? In order to use that data do your new system’s data model needs to keep them as well. Watch out, it may mean also a nasty synchronization! If one of answers is yes, you will need a potential data migration. Just continue to get more details. 2. How to capture requirements and define business rules? If you determine that you need a data migration, be careful and specify at least following details in your analysis.   2.1 Identify if your company have multiple data sources for that entities. If yes, determine the master and the fate of other systems’ data. You will see how many systems you are dealing with. It is important to know how and where data is stored, backed up, and if it is archived. 2.2 Data profiling: Data profiling is a “must have” activity to understand what are specs of the material you will be working on. Conduct profiling activities and classify the data, such as data with missing unique ID’s or missing first name and last name or false data such as numeric values as first name and other useful information like length, type, candidate for primary key, etc. Results of the profiling will guide you to design user interfaces and capture business rules. 2.3 Do you need data cleansing? According the data profiling, you will see if you need cleansing activities and what will be the final structure of the data you will be working on. Also you will be able to clarify cleansing related activities on the project timeline which will provide a cleaner vision for the project timeline. If your answer is no, definitely check the section 2.6. 2.4 Data structures must be well understood if your project requires design of user interfaces or data forms. Consider data structures while determining dynamic user interfaces or form context. For example, old system may store the phone number and its extension in one field by separating data by “–“. This means two numbers are stored in one field and you should consider such constraints while you are designing a new interface with multiple fields on section 2.8 or determine ways to separate phone number and its extension effectively while moving the data as mentioned on section 2.7. 2.5 Fate of the historical data:  Take into account if historical data will be migrated or not. It may affect your user interfaces or business processes. 2.6 Fate of the missing or dirty data: After profiling, most probably you will see that some of your data is not clean or adequate to use in further actions. For example, you are working on sensible customer data and national identity number is mandatory but some records do not have identity numbers. It will cause you problems to pinpoint the customer or you will face further problems if this information is mandatory to display customer on the screen.  Even worse, if you have validations based on the identity number such as debt control or billing, the system will not be able to conduct such validations. Always check whether data ownership belongs to a specific business unit. If yes, let them decide to the fate of data. Decide whether the data is just enough to use or will it cause problems to conduct business processes. Will you migrate such data? If yes, sections 2.8 and 2.10 will be highly important for you. Is it possible to clean or enhance problematic data somehow? If yes, how? Determine the way and related requirements. If you decide not to move such data, always consult with your business unit for possible further actions. They may need to find the customer and inform him/her legally according his/her account status or they may need another manual/automation processes.  2.7 Data mapping is basically the activity of creating a map of the existing data model by matching each entity&field with the future data model. Each entity should be mapped correctly and in details to be able to move data successfully. The map is an essential item of data migration strategy which is a whole another topic and not be mentioned here in details. Based on the mapping, you can see the gap between your legacies and your future and you can use the information on section 2.8 2.8 Screen validations and rules: Results of sections 2.2-2.7 will give you clear information about user interface validations and potential need of new business processes. 2.8.1 Screen validations? Define entity specs such as type and length based on the profiling results, the information will guide you to design potential data forms. Define the rules for the gap. If entities are not matching neatly, define UI standards and validation rules accordingly. Such as, will be these entities optional or if two different data are kept in one field, will you continue to collect and display them together? 2.8.2 New processes is needed? If you decided to transport problematic data; You may need to create new processes to correct such data. For example if the identity number is mandatory and your customer update process originally does not allow to update the number, in order to enable the correction of the customer information, you may need the define rules such as displaying identity number field editable. You may create new processes to alert the system or trigger different actions. 2.9 Define security & security measures such as encryption. If data needs to be migrated encrypted, general rules shall be set during analysis phase. 2.10 Define migration acceptance criteria such as data quality, migration duration etc. if it will cause termination on your services 2.11 Define the fate of the legacy data: Will you continue to keep the data on the legacy systems? If yes, determine whether a synchronization is needed with the new system or not? How long the data should be kept on legacy system? What are maintenance rules?   3.    What is next? Of course, plan the future! All answers will guide you for further activities which need to be added to the project plan in details. Identifying these steps at the beginning will prevent you from future unexpected surprises and definitely will help to close the project on time. 3.1 Rehearsals A clean migration needs rehearsals where you can have a look at your situation. 3.2 Testing scenarios Requirements need to be tested and since migration activity creates its own requirements, testing scenarios should cover these requirements as well. Author: Aylin Şen, Senior Business Analyst aylinsen Thu, 28 May 2015 16:49:00 GMT f1397696-738c-4295-afcd-943feb885714:3287 https://modernanalyst.com/Resources/Articles/tabid/115/ID/2495/The-3-Amigos--BA-QA-and-Developer.aspx#Comments 0 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=2495 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2495&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/2495/The-3-Amigos--BA-QA-and-Developer.aspx The 3 Amigos (sometimes referred to as a “Specification Workshop”) is a meeting where the Business Analyst presents requirements and test scenarios (collectively called a “feature”) for review by a member of the development team and a member of the quality assurance team. ryanhewitt Wed, 17 Dec 2014 19:29:00 GMT f1397696-738c-4295-afcd-943feb885714:2495 https://modernanalyst.com/Resources/Articles/tabid/115/ID/2926/Specifying-Quality-Requirements-With-Planguage.aspx#Comments 0 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=2926 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2926&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/2926/Specifying-Quality-Requirements-With-Planguage.aspx How often has a customer asked you to write software that is user-friendly, robust, fast, or secure? No one will argue that those are worthy goals that everyone wants in their software products. However, they are terrible requirements. They give you no idea of just what “user-friendly” means, or how to tell if you’ve achieved the desired characteristics that mean “user-friendly” to a particular customer. Transform VA Mon, 21 Apr 2014 09:50:00 GMT f1397696-738c-4295-afcd-943feb885714:2926 https://modernanalyst.com/Resources/Articles/tabid/115/ID/1581/Getting-the-Most-out-of-Your-Beta-Launch.aspx#Comments 0 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=1581 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1581&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/1581/Getting-the-Most-out-of-Your-Beta-Launch.aspx Before an organization releases a new piece of software or web feature to all of its customers or the general public, it will generally offer a limited audience a chance to test drive the feature and offer their feedback. This is generally known as a Beta launch... speeditonline Wed, 06 Feb 2013 09:21:00 GMT f1397696-738c-4295-afcd-943feb885714:1581 https://modernanalyst.com/Resources/Articles/tabid/115/ID/1967/A-Proposal-for-an-Agile-Development-Testing-V-Model.aspx#Comments 2 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=1967 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1967&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/1967/A-Proposal-for-an-Agile-Development-Testing-V-Model.aspx This article proposes a V-Model for agile development testing and invites feedback from the reader. The agile method used in this article is Scrum; the author assumes the reader is familiar with this solution development life cycle. speeditonline Sun, 23 Oct 2011 19:03:00 GMT f1397696-738c-4295-afcd-943feb885714:1967 https://modernanalyst.com/Resources/Articles/tabid/115/ID/1858/Dreaming-Of-A-Business-Analyst-Career-A-Personal-Journey-From-QA-To-BA.aspx#Comments 3 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=1858 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1858&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/1858/Dreaming-Of-A-Business-Analyst-Career-A-Personal-Journey-From-QA-To-BA.aspx We BA's are occasionally asked, "What do you do?" I try to make a joke out of this innocent question by replying, "Well, what would YOU do with English and writing degrees? I'm a Business Analyst of course." People don’t laugh. speeditonline Mon, 06 Jun 2011 07:24:00 GMT f1397696-738c-4295-afcd-943feb885714:1858 https://modernanalyst.com/Resources/Articles/tabid/115/ID/1235/Using-Extreme-Inspections-to-Significantly-Improve-Requirements-Practice.aspx#Comments 6 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=1235 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1235&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/1235/Using-Extreme-Inspections-to-Significantly-Improve-Requirements-Practice.aspx Extreme Inspections are a low-cost, high-improvement way to assure specification quality, effectively teach good specification practice, and make informed decisions about the requirements specification process and its output, in any project. The method is not restricted to be used on requirements analysis related material; this article however is limited to requirements specification. It gives firsthand experience and hard data to support the above claim. Using an industry case study I conducted with one of my clients I will give information about the Extreme Inspection method - sufficient to understand what it is and why its use is almost mandatory, but not how to do it. I will also give evidence of its strengths and limitations, as well as recommendations for its use and other applications. adrian Wed, 03 Feb 2010 05:01:00 GMT f1397696-738c-4295-afcd-943feb885714:1235 https://modernanalyst.com/Resources/Articles/tabid/115/ID/617/Putting-the-User-Back-in-User-Acceptance-Testing.aspx#Comments 3 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=617 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=617&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/617/Putting-the-User-Back-in-User-Acceptance-Testing.aspx Why is it so challenging to get users involved in User Acceptance Testing (UAT)? Isn’t it called UAT because the users are the main participants? My experience has shown that involving users in all phases of the project, especially UAT, is the best way to ensure project success. This article will present a proven approach to increasing user involvement by addressing the problems with traditional approaches to UAT.   I recently worked on a project in which a major defect was found after the software application moved to production. This defect caused the users to perform three days of manual processes. Users on the IT project team worked countless overtime hours. The defect also resulted in a frustrated user group and business sponsor. The project team’s morale was low and the business users lost a great deal of confidence in the project team’s ability to deliver quality software solutions. To reduce the risk of making this crucial mistake in the future the project team improved the UAT approach by getting users more involved. admin Sat, 06 Dec 2008 17:00:00 GMT f1397696-738c-4295-afcd-943feb885714:617 https://modernanalyst.com/Resources/Articles/tabid/115/ID/622/Managers-Guide-to-User-Acceptance-Testing.aspx#Comments 0 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=622 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=622&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/622/Managers-Guide-to-User-Acceptance-Testing.aspx For most businesses and organisations, if IT stops, the business stops. Whenever a company turns on a new production line, opens a new retail store, launches a new product or provides a new service, there is invariably a new or modified IT system behind it. Going live is the culmination of time, effort, resources and finance. A problem-free IT system is the “acid test” of significant, often crucial investment. Whilst the technical testing of IT systems is a highly professional and exhaustive process, testing of business functionality is an entirely different proposition. Does the system deliver the business functions that are required – does it follow the company’s business rules – does it support a government department’s obligations - does it cope with exceptions? The people who have to make these decisions – to accept or reject the new system – are the business users. It is therefore critical to get the business user involved in testing and not rely only on the technicians. In this paper we explore the rationale behind User Acceptance Testing (UAT), why it is so important, and how best to go about it. Author: Jan Kusiak pddean Tue, 02 Dec 2008 02:13:00 GMT f1397696-738c-4295-afcd-943feb885714:622 https://modernanalyst.com/Resources/Articles/tabid/115/ID/463/Eight-Competencies-a-Business-Analyst-Needs-to-Know.aspx#Comments 12 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=463 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=463&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/463/Eight-Competencies-a-Business-Analyst-Needs-to-Know.aspx Failing to properly and accurately define requirements at the very beginning of the project lifecycle points to a distinct lack of business analysis competency. The role of the business analyst is an important one, and, sadly, one that is underutilized by many organizations around the world. In essence, a business analyst acts as a translator or liaison between the customer or user and the person or group attempting to meet user needs. But, that’s just speaking generally. What about the specifics? Below, I’ve put together a list of eight key competencies that every business analyst—or every professional performing the duties of a business analyst—should possess. I’ve included specific emphasis on tasks associated with junior, intermediate and senior business analysts. If performed effectively, the items on this list could save organizations millions. adrian Tue, 08 Jul 2008 02:30:00 GMT f1397696-738c-4295-afcd-943feb885714:463 https://modernanalyst.com/Resources/Articles/tabid/115/ID/316/Who-Does-QA-Hint-Not-your-testers.aspx#Comments 0 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=316 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=316&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/316/Who-Does-QA-Hint-Not-your-testers.aspx Many of us have Quality Assurance (QA) groups in our organizations, and the natural assumption might be that these groups are responsible for the quality of our products. For a few of us, that assumption might hold true, but for most organizations, the QA group cannot be held responsible for quality because they don't actually assure quality. What they do is test. Author: Allan S. Koch, PMP lilesj Wed, 26 Mar 2008 15:56:00 GMT f1397696-738c-4295-afcd-943feb885714:316 https://modernanalyst.com/Resources/Articles/tabid/115/ID/310/Never-Let-a-Good-Editor-Go.aspx#Comments 0 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=310 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=310&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/310/Never-Let-a-Good-Editor-Go.aspx When documenting systems, quality assurance requires quality support people, especially final content editors. They are worth their weight in gold-edged certificates. If you are part of a large project that has a very large documentation aspect, learn to nurture, develop and retain a good editorial staff, and do not forget to keep everyone's skills current on the tools you are using! The current crop of word processor and presentation software packages are constantly adding features to make your life easier.   Author: David Egan, RHCE, PMP lilesj Wed, 26 Mar 2008 14:54:00 GMT f1397696-738c-4295-afcd-943feb885714:310